Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

[External] - VMware Cloud on AWS - Getting Error: The attempted operation cannot be performed in the current state ("Powered on"). (76859)

Last Updated: 3/21/2024Categories: How toTotal Views: 2893Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

When a Virtual Machine workload has been migrated via VMware HCX RAV (Replicated-Assisted vMotion) migration type, when trying to expand a disk one can get the following error:

The attempted operation cannot be performed in the current state ("Powered on").

The above error may also be experienced for newly provsioned (newly created) VMs running on SDDC Version 1.8v3, this would be expected and this issue would be resolved and fixed iin a future SDDC release.

Purpose

To follow the workaround section in order to continue being able to expand a disk for the affected virtual machine.

Cause

Root cause for error message: The attempted operation cannot be performed in the current state ("Powered on").
It is likely that these VMs were migrated via RAV - Replicated-Assisted vMotion (migration method in HCX). And this is due to an issue in path conversion behavior - we provide different behavior for absolute and relative datastore path format. When we get an absolute path like this: "[]/vmfs/volumes/vsan:UUID/OtherDisk/disk1.vmdk", we will (attempt to) do a full canonicalization, but when we get a relative path like this: "[vsanDatastore] OtherDisk/disk1.vmdk", we do not canonicalize the relative part of the path.  So when we do canonicalization, we call realpath, but it will fail because the file doesn't exist yet during creation, so we fall back to the uncanonicalized path. Because of this, this where where we do the workaround of creating/deleting the snapshot of the VM, or power-down the VM and edit the disk settings (which fixes the path call logic in the cloud vCenter).

Resolution

The long-term resolution will be fixed in an upcoming VMware Cloud on AWS SDDC version release.

Workaround

Workaround Workflow 1:
a. Select VM Name
b. Right-click --> "Power-off" or "Shutdown Guest OS"
c. Select "Edit VM settings" and scroll down to "Hard Disk" section to expand the disk to preferred disk size

or

Workaround Workflow 2:
(Under the  assumption that the VM workload would be left powered-on/running)

a. Select VM Name
b. Right-click --> "Snapshots" --> "Take Snapshot" (Snapshot the virtual machine's memory can be UNCHECKED)
c. Allow the snapshot to be created
d. Right-click the VM name (from #1), --> Select "Delete All Snapshots"
e. Re-attempt in expanding the disk through native cloud vCenter UI for the RAV migrated VM, expanding the disk will work as expected now

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
Update Manager 6.5.x を使用したパッチ定義のダウンロードで、「パッチ定義をダウンロードできません (Cannot download patch definitions)」というエラーが発生する (77026)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Cloud on AWS

Related Versions:

Take Our Survey

Support Assistant